Demonstrate the ability to write technical reports and research proposals, and to present research findings effectively; and to engage with the evaluation and protection of research outputs.
This is the terminal competency of the research proposal development cycle: the ability to present, defend and refine a proposal under conditions of critical scrutiny.
These notes treat presentation not as a soft skill peripheral to research, but as a scientific act in its own right — a form of scholarly argumentation where evidence, structure, rhetoric and visual design converge.
The lecture is organised in four pillars, and Sections 4–8 follow them: A architecture of the talk, B audio-visual aids, C communication, D alignment with evaluation criteria.
Read Section 8 first if you are short of time. The rubric determines where your preparation effort should go, and it is not where most students put it.
1. Learning Outcomes
- Design and structure a research presentation that aligns with academic review standards.
- Select and deploy audio-visual aids in a manner that reinforces, rather than replaces, oral communication.
- Demonstrate effective verbal and non-verbal communication skills during a scholarly defence.
- Anticipate, classify and respond competently to questions raised by review committee members.
- Decode the evaluation rubrics commonly employed by review committees and align the presentation accordingly.
2. Presentation as a Scientific Act
A research proposal, however scientifically rigorous, remains incomplete until it is communicated effectively to its intended audience. The culminating event in the lifecycle of a proposal is its defence before a Review Committee — a panel of experts drawn from academia, industry and, in funded projects, funding agencies.
The committee’s task is not merely to accept or reject the proposal. It is to interrogate its assumptions, methodology, novelty, feasibility and potential impact.
Students who internalise this stop treating hard questions as personal attacks. Every question is scrutiny of the work, not of you.
The lecture is anchored in four pillars, each treated with reference to peer-reviewed communication research and to standard practice in computer science research communities such as IEEE, ACM and AAAI:
- Pillar A — architectural design of the presentation.
- Pillar B — multimodal communication through audio-visual aids.
- Pillar C — interactive competence, particularly the handling of queries.
- Pillar D — strategic alignment with evaluation criteria.
3. Key Concepts and Definitions
| Term | Definition |
|---|---|
| Review committee | A formally constituted panel of subject-matter experts tasked with evaluating the scientific merit, feasibility and impact of a research proposal |
| Presentation | A structured, time-bound oral exposition of a research proposal, supported by visual media and followed by a question-and-answer session |
| Audio-visual aids | Tools and media — slides, videos, animations, whiteboards, live demonstrations — that supplement oral communication |
| Rubric | A scoring framework comprising explicit criteria, performance descriptors and weightage, used to assess proposals systematically |
| Elevator pitch | A 60–90 second distillation of the research problem, motivation and expected contribution, used at the opening of a presentation |
| Back-pocket slide | A supplementary slide held in reserve to answer an anticipated detailed query without disrupting the flow of the main presentation |
| Stage fright management | Cognitive and physiological techniques for controlling performance anxiety during public scholarly communication |
4. Pillar A — Designing the Presentation
4.1 The 10/20/30 Rule
A widely cited heuristic for academic presentations, originally proposed by Guy Kawasaki and refined for academic contexts by Garr Reynolds:
- 10 slides maximum, for a 20-minute talk.
- 20 minutes maximum speaking time.
- 30-point font minimum, ensuring legibility from the back of any standard lecture hall.
For a typical B.Tech project review of 15 minutes, the optimal structure is 8–10 slides.
4.2 Canonical Structure for a Proposal Presentation
A defensible structure mirrors the proposal document but is compressed for oral delivery.
| Slide | Content | Time | Strategic purpose |
|---|---|---|---|
| 1 | Title, author(s), affiliation, guide, date | 30 sec | Establishes identity and context |
| 2 | The elevator pitch / problem statement | 90 sec | Hooks the committee and frames urgency |
| 3 | Motivation and background | 90 sec | Establishes the why now |
| 4 | Literature gap and research question(s) | 2 min | Demonstrates awareness of the state of the art |
| 5 | Objectives / hypothesis | 1 min | Crystallises the contribution claim |
| 6 | Proposed methodology | 3–4 min | The intellectual core of the talk |
| 7 | Expected outcomes / preliminary results | 2 min | Demonstrates progress and feasibility |
| 8 | Work plan and timeline (Gantt chart) | 1 min | Establishes realism of execution |
| 9 | References — selected, key 5–6 | 30 sec | Signals scholarship |
| 10 | Acknowledgements and Q&A invitation | 30 sec | Closes gracefully |
Note where the time goes: methodology takes a fifth of the talk, matching its weight in the rubric in Section 8.
4.3 Single Idea per Slide
Each slide should communicate one dominant cognitive unit. The cognitive load theory of multimedia learning (Mayer, 2009) holds that working memory can process approximately 4 ± 1 chunks of information simultaneously; overloading a slide with multiple ideas measurably reduces comprehension. This is a principled reason for the rule, not an aesthetic preference.
4.4 Time Discipline
Most committees interpret an overrun as one or more of: lack of rehearsal, poor understanding of one’s own work, or disrespect for the committee’s schedule.
The safe strategy: rehearse to 80 percent of the allotted time, leaving 20 percent as buffer for the natural expansion that occurs under questioning.
Applied: a 15-minute slot means rehearsing to 12 minutes. If your rehearsal runs to 15, you will finish at 19 on the day — and be stopped at 15.
5. Pillar B — Audio-Visual Aids
5.1 Typology of AV Aids
- Static visual — slides (PowerPoint, Beamer, Google Slides), posters, printed handouts.
- Dynamic visual — animations and transitions, live system demonstration, video clips, code walk-throughs in an IDE.
- Auditory — spoken narration, audio clips, music (rare and context-specific).
- Hybrid — interactive simulations, live polling tools (Mentimeter, Slido), augmented and virtual reality demonstrations.
5.2 The CRAP Framework for Slide Design
Following Tufte’s principles of graphical integrity and Mayer’s multimedia learning principles:
- Contrast — high contrast between text and background: dark text on light, or light on dark. Nothing in between.
- Repetition — consistent fonts, colours and layouts across slides.
- Alignment — every element should be visually connected to at least one other element.
- Proximity — group related items spatially; closeness is the claim of relationship.
5.3 Typography and Colour
- Title font: 28–32 pt, bold. Body font: 22–24 pt, regular. Caption or footnote: not less than 18 pt.
- Prefer sans-serif families — Calibri, Arial, Helvetica, Lato. They render better than serifs at projection distance.
A 60-30-10 colour scheme is academically appropriate: 60 percent dominant colour (typically a white background or the institutional colour); 30 percent secondary colour for headings and emphasis; 10 percent accent colour for highlighting novel contributions and key results. Colour-blind-friendly palettes — viridis, ColorBrewer — should be preferred wherever graphs and charts appear.
If everything on the slide is highlighted, the committee cannot see what you think your contribution is. Reserve the 10 percent for the claim you want them to remember.
5.4 Five Common Pitfalls
| Pitfall | Consequence | Mitigation |
|---|---|---|
| Reading verbatim from slides | Loss of audience engagement; committee perceives lack of depth | Use slides as prompts, not scripts |
| Excessive animation | Cognitive distraction | Animate only to reveal a stepwise process |
| Low contrast / small fonts | Committee members at the back cannot read | Test from the back row during rehearsal |
| Cluttered graphs | Loss of insight | Apply Tufte’s data-ink ratio: maximise information, minimise chartjunk |
| Embedding entire paragraphs | Information overload | Replace prose with structured bullets and visuals |
It is self-reinforcing. Slides written as a script produce a presenter who must read them, which produces a committee that concludes you do not know your own work. The fault is in the slide design, not in the presenter’s memory.
5.5 Demonstrations — When and How
A live system demonstration can be a powerful differentiator, but it carries risk. Best practice:
- Pre-record the demo as a video in case the live version fails.
- Use a sandbox environment with pre-loaded data.
- Keep the demo under 90 seconds within the main presentation; longer demos move to the appendix and play only if requested.
- Have a fallback slide summarising the demo’s outcome.
5.6 Tools in Academic CS Presentations
- Beamer (LaTeX) — publication-quality slides; ideal for theory-heavy talks.
- PowerPoint / Keynote — versatile, widely supported, suitable for design-rich content.
- Google Slides — collaborative preparation; cloud-based accessibility.
- Overleaf + Beamer — integration of manuscript and presentation visuals.
- Marp, RevealJS — Markdown-based slide frameworks for technically literate presenters.
- OBS Studio, Loom — for pre-recording demonstrations.
- draw.io, Lucidchart — for architecture and workflow diagrams.
- Matplotlib, Seaborn, Plotly — for figures consistent with the proposal document.
6. Pillar C — Communication Skills
6.1 Pace and Pausing
- Optimal speaking rate: 130–150 words per minute — deliberately slower than conversational speech.
- Strategic pauses of 1.5–2 seconds after key claims allow the committee to absorb and reflect.
- Filler words (um, uh, like, you know) should be minimised; a silent pause is always preferable to a filled one.
6.2 Articulation and Pronunciation
Particularly relevant for computer science terms that are often mispronounced. Settle yours in rehearsal, not at the podium: LaTeX (LAH-tek or LAY-tek), GIF (soft G, contested), Ubuntu (oo-BOON-too), et al., ibid. (IB-id), viz. (namely, videlicet).
6.3 Vocal Variation
Monotone delivery measurably reduces retention. Use pitch variation to signal meaning: rising pitch for curiosity, open-ended statements and questions; falling pitch for definitive claims and conclusions; lowered pitch for emphasis on a critical claim.
6.4 Non-Verbal Communication
Albert Mehrabian’s communication model is frequently over-applied, but its useful core holds: a large share of meaning in face-to-face communication is conveyed non-verbally.
- Eye contact — distribute gaze across all committee members; avoid fixating on a single member or on the screen.
- Posture — upright, open stance; avoid crossed arms or leaning on the podium.
- Gestures — use hands to indicate transitions, enumerate points, or point to specific slide regions.
- Movement — confined but purposeful; do not pace.
- Facial expression — convey confidence and enthusiasm; smile at the opening and during acknowledgements.
6.5 The Opening — First Sixty Seconds
The committee’s first impression is formed rapidly and is highly durable (the primacy effect). Four effective openings:
- A provocative question: “What if a neural network could explain its own decisions to a radiologist in real time?”
- A striking statistic: “Globally, 2.5 quintillion bytes of data are generated daily, yet 80% remains unstructured and unanalysed.”
- A compelling narrative: a brief anecdote of a real-world failure that motivates the research.
- A clear thesis: “This work proposes a novel federated learning framework that reduces communication overhead by 40% while preserving differential privacy guarantees.”
6.6 The Closing — Four Sentences
A weak closing undermines the strongest presentation. The closing must echo the opening. Recommended pattern:
- Summary of contribution (one sentence).
- Restatement of impact (one sentence).
- Forward-looking statement (one sentence).
- Invitation for questions (one sentence).
“In summary, we have presented a lightweight intrusion detection system for IoT networks that achieves 96.4% accuracy with 60% lower computational cost than the state of the art. This has direct implications for smart-city deployments. We will extend this to edge-fog architectures in the next phase. We welcome your questions and feedback.”
6.7 Managing Stage Fright
Stage fright is a documented physiological response mediated by the amygdala’s release of adrenaline. It is not a character flaw and it is not evidence that you are unprepared. It is managed, not eliminated. Evidence-based techniques:
- Cognitive reappraisal — reframe the presentation as a scholarly conversation, not a performance. You are the person in the room who has read the most about this problem.
- Systematic desensitisation — rehearse repeatedly in increasingly realistic conditions: alone, then to a peer, then in the actual room with the actual projector.
- Physiological regulation — box breathing (4-4-4-4), progressive muscle relaxation.
- Preparation ritual — arrive early, test equipment, walk the room. Most acute pre-talk anxiety is displaced logistical anxiety.
- Power posing — research support is contested, but the psychological priming effect is real enough to be worth two minutes.
- Hydration and rest — avoid stimulants before the talk. Caffeine converts nervousness into a visible tremor and an accelerated speaking rate.
7. Pillar D — Handling Queries
7.1 Taxonomy of Committee Questions
Understanding the type of question is the first step to handling it competently, and it takes under a second.
| Question type | Intent | Example | Strategy |
|---|---|---|---|
| Clarification | Confirm understanding | “Could you clarify what you mean by ‘embedding space’?” | Paraphrase the question before answering; provide a concise definition |
| Probing | Test depth of understanding | “Why did you choose the Adam optimiser over SGD for this model?” | Explain trade-offs; admit limitations if appropriate |
| Challenging | Test defensibility of claims | “Your baseline comparison is weak; have you considered X?” | Acknowledge the validity; defend or concede gracefully |
| Speculative | Explore extensions | “Could this method generalise to time-series data?” | Distinguish present scope from future work; commit if plausible |
| Procedural | Clarify logistics | “What is your data acquisition timeline?” | Answer directly; refer to the work plan slide |
Answering a challenging question as though it were a clarification — or the reverse — is how otherwise well-prepared candidates lose control of a defence.
7.2 The IDEAL Framework for Query Response
- I — Interpret. Repeat or paraphrase the question to ensure accurate understanding. “If I understand correctly, you are asking whether our approach handles concept drift…” This is the step students skip, and the one that buys thinking time.
- D — Declare. State your position clearly. “Yes, we have addressed this through…” or “That is a limitation we acknowledge…”
- E — Evidence. Support with data, citations or logical reasoning.
- A — Assess. Evaluate the implications. “This means our model can…”
- L — Link back. Connect to the broader proposal narrative.
7.3 When You Do Not Know the Answer
Intellectual honesty is paramount. The committee is testing integrity as much as knowledge. Recommended response:
- Acknowledge clearly: “That is an excellent point, and I do not have a definitive answer at this moment.”
- Demonstrate awareness: “However, I am aware of related work by [Author] that suggests…”
- Commit to follow-up: “I will investigate this and revert with a written response within the week.”
Fabricating an answer is the single most damaging error a presenter can make. An honest “I do not know, and here is how I will find out” costs a fraction of what an invented answer costs when the committee follows it up.
7.4 Handling Hostile or Aggressive Questions
- Stay calm. Do not raise your voice or show visible irritation.
- Validate the question. “I appreciate the rigour of your scrutiny.”
- Re-route to substance. Focus on the technical merit, not the interpersonal dynamic.
- Appeal to data. “The empirical evidence suggests…”
- Defer to your guide if the question lies outside your scope: “That is a strategic decision my supervisor and I will discuss; my immediate understanding is…”
7.5 The Back-Pocket Slide Strategy
Anticipate five to seven likely technical questions and prepare supplementary slides containing the relevant data, equations or diagrams. These are kept after the visible slide deck, or in a separate file, and brought up only when needed. This demonstrates preparedness without disrupting the narrative flow — and a presenter who can produce a convergence proof sketch on request has effectively ended that line of questioning.
8. Understanding Evaluation Criteria
8.1 Generic Rubric for Proposal Review
The following synthesises criteria used by UGC, DST-SERB, AICTE, IEEE student grants and similar bodies.
| Criterion | Typical weight | What committees look for |
|---|---|---|
| Methodology | 20–25% | Scientific rigour; appropriateness of methods; reproducibility |
| Novelty and originality | 15–20% | Clear articulation of what is new; differentiation from prior work |
| Problem definition and motivation | 10–15% | Clarity of problem statement; significance to discipline or society |
| Literature review | 10–15% | Coverage of seminal and recent work; identification of gaps |
| Feasibility and work plan | 10–15% | Realistic timeline; access to resources; risk mitigation |
| Expected outcomes and impact | 10–15% | Clarity of deliverables; academic and societal value |
| Presentation quality | 5–10% | Clarity, visual design, time management, Q&A handling |
| Ethics and compliance | 5% | IRB / IEEE ethics, data privacy, plagiarism declarations |
Methodology and novelty together account for up to 45 percent. Presentation quality — the thing students rehearse most — is at most 10 percent.
This is deliberately uncomfortable, and it is the most actionable fact in the lecture: preparation effort should follow the weights. A beautifully delivered talk about a weakly justified method scores badly.
8.2 Differentiating Rubrics
- Academic project review (internal) — emphasis on methodology, learning outcomes and demonstration.
- Thesis proposal defence — emphasis on literature review, contribution and methodological soundness.
- Funding agency review (DST, SERB, industry grants) — emphasis on broader impact, budget justification, deliverables and societal benefit.
- Conference paper presentation — emphasis on novelty, technical depth and engagement.
8.3 Decoding Reviewer Comments
Committee reports typically contain three classes of remark:
- Mandatory corrections — comments that must be addressed before approval, such as a methodological flaw or missing ethical clearance. These determine acceptance.
- Suggested improvements — comments that strengthen the proposal if addressed, such as an additional baseline comparison. These determine quality.
- Appreciative remarks — comments that validate the approach and signal confidence. These provide strategic guidance for publication.
8.4 Strategic Alignment — the Weighted Opener
Before the presentation, identify which two or three criteria carry the highest weight in the given context, and design the talk to maximise scores in those areas.
- For a DST-SERB proposal, lead with societal impact and deliverables.
- For a thesis defence, lead with methodological rigour and literature positioning.
- For an industry-sponsored project, lead with commercial viability and scalability.
This strategic framing is sometimes called the weighted opener technique.
9. Worked Example: A 15-Minute CS Project Review
Consider a B.Tech final-year project on Privacy-Preserving Federated Learning for Healthcare IoT, assessed against the rubric in Section 8.
- Title — project title, team of four students, supervisor Dr. X, Department of Computer Science, UPES, May 2025. Clean institutional template.
- Problem — “Hospitals cannot share patient data due to HIPAA/GDPR, yet AI models require large datasets. How can we train a robust diagnostic model without centralising data?” Visual: split screen of two hospitals with a “no data sharing” lock icon.
- Background — global healthcare data breaches 2018–2024 (graph); growth of federated learning publications (graph). Key insight in one bullet: “FL eliminates central data aggregation, but introduces privacy, communication and heterogeneity challenges.”
- Gap — three papers summarised in three columns (FedAvg, FedProx, SCAFFOLD) with their limitations. Visual: Venn diagram showing the intersection of challenges none of them fully address.
- Objectives — (1) design a differential-privacy-aware FL framework; (2) reduce communication rounds by 40%; (3) validate on three healthcare benchmarks.
- Methodology — architecture diagram (clients → secure aggregation → global server with DP noise). Equation θt+1 = θt − η∇LDP(θt; ξt). Workflow of five steps.
- Preliminary results — table comparing accuracy, communication rounds and privacy budget ε against baselines. The proposed method highlighted in a coloured cell.
- Work plan — Gantt chart for the remaining four months: experimentation (Jan–Feb), deployment (Mar), thesis writing (Apr).
- References — McMahan et al. 2017, Abadi et al. 2016, Kairouz et al. 2021.
- Closing — “We present a privacy-aware FL framework achieving 93.2% accuracy with 42% fewer communication rounds at ε = 1.0. We thank Dr. X, the IoT Lab, and welcome your questions.”
- BPS-1 — detailed convergence proof sketch.
- BPS-2 — privacy budget analysis under composition theorems.
- BPS-3 — comparison with FedBN for non-IID data.
- BPS-4 — hyperparameter sensitivity plots.
10. Ten Common Errors to Avoid
- No rehearsal. The most common cause of a poor review.
- Apologising at the start. “Sorry, I’m nervous” undermines confidence before the talk begins.
- Reading slides. Suggests lack of depth.
- Overuse of jargon. Define technical terms on first use.
- No clear takeaway. Every slide should advance the central thesis.
- Hiding limitations. Committees will find them; pre-empt them.
- Plagiarism in slides. Reuse figures only with proper attribution; this is a serious ethical violation.
- Ignoring the guide’s role. Acknowledge supervisor contributions explicitly.
- Disrespecting time. Going significantly over time forfeits goodwill.
- Adversarial tone during Q&A. Treat every question as an opportunity, not an attack.
They are research-integrity faults that happen to surface in a presentation, and they connect directly to the Unit III material on plagiarism and attribution. Hiding a limitation the committee then discovers damages trust in every other claim you have made.
11. Summary
- Architectural design of the presentation must mirror the proposal structure while respecting severe time constraints. Rehearse to 80 percent of the slot.
- Audio-visual aids function as cognitive scaffolding, not as scripts. Their design must obey contrast, repetition, alignment and proximity; 30-point minimum; 60-30-10 colour.
- Communication skills encompass verbal, vocal and non-verbal channels. The opening and the closing carry disproportionate weight through primacy and recency.
- Handling queries requires classification of the question type, structured response through the IDEAL framework, and intellectual honesty when the answer is unknown.
- Never fabricate an answer. Integrity is being tested alongside knowledge.
- Methodology and novelty are up to 45 percent of the rubric; presentation quality is at most 10. Allocate preparation effort accordingly.
12. Exam Preparation
- Internalise the rubrics of your own institution; request sample rubrics from past defences from your department’s review committee office.
- Record yourself delivering a 10-minute talk and review the video for filler words, posture and pacing.
- Prepare for at least 15 anticipated questions and rehearse the answers aloud.
- Use the elevator pitch framework to articulate your thesis in 60 seconds.
- Conduct a mock review with peers acting as committee members; rotate roles to understand the reviewer’s perspective.
- Review IEEE and ACM presentation guidelines for the venue of any future conference presentation.
12.1 Short-Answer Questions
- State and explain the 10/20/30 rule. In what scenario is it inapplicable? 3 marks
- Differentiate between clarifying, probing and challenging questions. Provide one example of each from a CS research context. 3 marks
- List Mayer’s principles of multimedia learning and indicate how each applies to slide design. 4 marks
- What are the three categories of remark in a committee report, and how should the presenter respond to each? 3 marks
- Explain the IDEAL framework for query handling with an example from your own domain. 4 marks
- State the CRAP framework and give one slide-design consequence of each element. 4 marks
- What is a back-pocket slide, and what problem does it solve? 2 marks
12.2 Long-Answer and Analytical Questions
- You are presenting a proposal on “Deep Reinforcement Learning for Autonomous Traffic Signal Control” to a committee comprising a control theorist, an urban planner and an AI researcher. Design the slide structure, anticipate seven questions (at least two from each reviewer’s domain), and propose back-pocket slides for each. 15 marks
- A senior committee member challenges your proposed methodology as “incremental and not publishable in a top-tier venue”. Outline, step by step, how you would respond using the IDEAL framework. What would you do if you privately agreed with the criticism? 10 marks
- Compare and contrast the evaluation rubrics of (a) a B.Tech project review committee and (b) a DST-SERB funding review committee. Identify the three criteria on which they diverge most sharply, and explain why. 10 marks
- Critically evaluate the following opening: “Hi everyone, my name is Rahul, and today I will present my project on machine learning. Sorry, I’m a bit nervous. So basically, my project uses CNN for image classification…” Rewrite it as a strong academic opening for a proposal on “Explainable CNN Architectures for Diabetic Retinopathy Detection”. 10 marks
12.3 Practical Exercise
Prepare a 10-slide deck for the proposal title “A Lightweight Blockchain-Based Framework for Secure Data Sharing in Vehicular Ad-hoc Networks (VANETs)”. The presentation must be 15 minutes long, address all canonical sections, and include annotations indicating what you would speak (in the speaker notes) versus what you would display (on the slide). Submit the deck along with a list of five anticipated questions and your prepared responses.
Mock review panel, 10 marks (CO2, CO4), with faculty and peer scoring. Use the slide-by-slide worked example in Section 9 as your template and prepare at least three back-pocket slides. You will be scored against the rubric in Section 8.1.
13. Suggested Reading
- Reynolds, G. (2019). Presentation Zen: Simple Ideas on Presentation Design and Delivery (3rd ed.). New Riders.
- Mayer, R. E. (2009). Multimedia Learning (2nd ed.). Cambridge University Press. The source of the cognitive-load argument in Section 4.3.
- Tufte, E. R. (2001). The Visual Display of Quantitative Information (2nd ed.). Graphics Press.
- Tufte, E. R. (2006). The Cognitive Style of PowerPoint (2nd ed.). Graphics Press.
- Alley, M. (2013). The Craft of Scientific Presentations: Critical Steps to Succeed and Critical Errors to Avoid (2nd ed.). Springer.
- Atkinson, C. (2018). How to Present When You’re Not a Trained Presenter. Harriman House.
- IEEE. (2022). IEEE Conference Presentation Guidelines. IEEE Communications Society.
- UGC. (2021). Guidelines for Research Proposal Evaluation. University Grants Commission, India.
- Kaur, A., & Singh, R. (2022). “Effective Communication Strategies for Engineering Research Defences.” IEEE Transactions on Education, 65(3), 412–425.
- Your own department’s review rubric. Request it before the panel — this is the single highest-value item on this list.